Dec 01 06:58:58.771 INFO testing okanon/rthrift_tutorial against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 01 06:58:58.771 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 06:58:59.185 INFO [stdout] 19bfe2e15303eca4ab3e3734c6c7632554d64e93d867a0136ec231f88479ed8e
Dec 01 06:58:59.193 INFO running `"docker" "start" "-a" "19bfe2e15303eca4ab3e3734c6c7632554d64e93d867a0136ec231f88479ed8e"`
Dec 01 06:59:00.502 INFO [stderr] usermod: no changes
Dec 01 06:59:00.563 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 06:59:00.563 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 06:59:00.563 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 06:59:00.563 INFO [stderr] files will be included as a binary target:
Dec 01 06:59:00.563 INFO [stderr] 
Dec 01 06:59:00.563 INFO [stderr] * /source/src/main.rs
Dec 01 06:59:00.563 INFO [stderr] 
Dec 01 06:59:00.563 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 06:59:00.563 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 06:59:00.563 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 06:59:00.563 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 06:59:00.563 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 06:59:00.563 INFO [stderr] 
Dec 01 06:59:00.563 INFO [stderr] For more information on this warning you can consult
Dec 01 06:59:00.563 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 06:59:00.631 INFO [stderr]    Compiling try_from v0.2.2
Dec 01 06:59:00.631 INFO [stderr]    Compiling threadpool v1.7.1
Dec 01 06:59:00.633 INFO [stderr]    Compiling ordered-float v0.3.0
Dec 01 06:59:00.633 INFO [stderr]    Compiling clap v2.27.1
Dec 01 06:59:03.039 INFO [stderr]    Compiling rthrift v0.11.0
Dec 01 06:59:28.663 INFO [stderr]    Compiling rthrift_tutorial v0.1.0 (/source)
Dec 01 06:59:35.214 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 34.68s
Dec 01 06:59:35.218 INFO [stderr] su: No module specific data is present
Dec 01 06:59:36.126 INFO running `"docker" "inspect" "19bfe2e15303eca4ab3e3734c6c7632554d64e93d867a0136ec231f88479ed8e"`
Dec 01 06:59:36.517 INFO running `"docker" "rm" "-f" "19bfe2e15303eca4ab3e3734c6c7632554d64e93d867a0136ec231f88479ed8e"`
Dec 01 06:59:36.771 INFO [stdout] 19bfe2e15303eca4ab3e3734c6c7632554d64e93d867a0136ec231f88479ed8e
Dec 01 06:59:36.774 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 06:59:37.383 INFO [stdout] 6046ed55db3288260941cd04aa9e6bcbc6056abe91e15731048b09f8a1b3646d
Dec 01 06:59:37.385 INFO running `"docker" "start" "-a" "6046ed55db3288260941cd04aa9e6bcbc6056abe91e15731048b09f8a1b3646d"`
Dec 01 06:59:38.249 INFO [stderr] usermod: no changes
Dec 01 06:59:38.295 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 06:59:38.295 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 06:59:38.295 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 06:59:38.295 INFO [stderr] files will be included as a binary target:
Dec 01 06:59:38.295 INFO [stderr] 
Dec 01 06:59:38.295 INFO [stderr] * /source/src/main.rs
Dec 01 06:59:38.295 INFO [stderr] 
Dec 01 06:59:38.295 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 06:59:38.295 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 06:59:38.295 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 06:59:38.295 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 06:59:38.295 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 06:59:38.295 INFO [stderr] 
Dec 01 06:59:38.295 INFO [stderr] For more information on this warning you can consult
Dec 01 06:59:38.295 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 06:59:38.351 INFO [stderr]    Compiling rthrift_tutorial v0.1.0 (/source)
Dec 01 06:59:41.146 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.87s
Dec 01 06:59:41.152 INFO [stderr] su: No module specific data is present
Dec 01 06:59:41.845 INFO running `"docker" "inspect" "6046ed55db3288260941cd04aa9e6bcbc6056abe91e15731048b09f8a1b3646d"`
Dec 01 06:59:42.034 INFO running `"docker" "rm" "-f" "6046ed55db3288260941cd04aa9e6bcbc6056abe91e15731048b09f8a1b3646d"`
Dec 01 06:59:42.334 INFO [stdout] 6046ed55db3288260941cd04aa9e6bcbc6056abe91e15731048b09f8a1b3646d
Dec 01 06:59:42.359 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 06:59:42.862 INFO [stdout] b822cbc055069a4e589c76890fd407f922b3c8808356b50883a65258bd853cd7
Dec 01 06:59:42.867 INFO running `"docker" "start" "-a" "b822cbc055069a4e589c76890fd407f922b3c8808356b50883a65258bd853cd7"`
Dec 01 06:59:43.803 INFO [stderr] usermod: no changes
Dec 01 06:59:43.851 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 06:59:43.852 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 06:59:43.852 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 06:59:43.854 INFO [stderr] files will be included as a binary target:
Dec 01 06:59:43.855 INFO [stderr] 
Dec 01 06:59:43.855 INFO [stderr] * /source/src/main.rs
Dec 01 06:59:43.855 INFO [stderr] 
Dec 01 06:59:43.855 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 06:59:43.856 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 06:59:43.856 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 06:59:43.856 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 06:59:43.857 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 06:59:43.857 INFO [stderr] 
Dec 01 06:59:43.857 INFO [stderr] For more information on this warning you can consult
Dec 01 06:59:43.857 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 06:59:43.899 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.06s
Dec 01 06:59:43.907 INFO [stderr]      Running /target/debug/deps/rthrift_tutorial-9f269b81520845c4
Dec 01 06:59:43.911 INFO [stderr]      Running /target/debug/deps/rthrift_tutorial_client-9a19c6b4b33b0a16
Dec 01 06:59:43.911 INFO [stdout] 
Dec 01 06:59:43.912 INFO [stderr]      Running /target/debug/deps/rthrift_tutorial_server-14511b9981847a72
Dec 01 06:59:43.912 INFO [stdout] running 0 tests
Dec 01 06:59:43.912 INFO [stderr]    Doc-tests rthrift_tutorial
Dec 01 06:59:43.912 INFO [stdout] 
Dec 01 06:59:43.913 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 06:59:43.913 INFO [stdout] 
Dec 01 06:59:43.913 INFO [stdout] 
Dec 01 06:59:43.913 INFO [stdout] running 0 tests
Dec 01 06:59:43.914 INFO [stdout] 
Dec 01 06:59:43.914 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 06:59:43.914 INFO [stdout] 
Dec 01 06:59:43.915 INFO [stdout] 
Dec 01 06:59:43.917 INFO [stdout] running 0 tests
Dec 01 06:59:43.917 INFO [stdout] 
Dec 01 06:59:43.917 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 06:59:43.917 INFO [stdout] 
Dec 01 06:59:44.775 INFO [stdout] 
Dec 01 06:59:44.775 INFO [stdout] running 0 tests
Dec 01 06:59:44.775 INFO [stdout] 
Dec 01 06:59:44.775 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 06:59:44.775 INFO [stdout] 
Dec 01 06:59:44.783 INFO [stderr] su: No module specific data is present
Dec 01 06:59:45.718 INFO running `"docker" "inspect" "b822cbc055069a4e589c76890fd407f922b3c8808356b50883a65258bd853cd7"`
Dec 01 06:59:45.975 INFO running `"docker" "rm" "-f" "b822cbc055069a4e589c76890fd407f922b3c8808356b50883a65258bd853cd7"`
Dec 01 06:59:46.171 INFO [stdout] b822cbc055069a4e589c76890fd407f922b3c8808356b50883a65258bd853cd7
